I have now checked that with the OpenLink Postgres Lite single tier
(direct to port 5432) driver the password entered at the dialog is
indeed passed to the driver and the connection succeeds. So it looks
like this problem might be with the pgsql-odbc driver (on MacOS X at
least).
mylog.. gives me:
[-1610609172]CC_connect: entering...
[-1610609172]CC_connect(): DSN = 'postgres', server =
'theservername', port = '5432', database = 'dbname', username =
'uname', password=''
This does not worry me as an application developer as I can always
present a login dialog from the application itself and build my own
connection string, but many third party applications will not do this.
Thanks
Giuliano
At 10:31 +0000 2003/03/05, Giuliano Gavazzi wrote:
>Dear all,
>
>I am not sure where this problem occurs, but using the iODBC driver
>manager and specifying the password in the login dialog (no Password
>parameter being set in the DSN) will result in pgsql-odbc getting an
>empty password in the connection string. If the Password parameter
>is specified in the DSN setup instead, it will be passed correctly.
>It looks like this might be a problem with iODBC, but it seems
>strange to me as it would have been noticed with other drivers too.
>Unfortunately I cannot check now that this is indeed not the case
>with the OpenLink own postgres driver.